				<div id="container" >
					<div class="grid_16">
						<div id="graph">
							<h2>Help</h2>
							<p>This page contains information about the usage and configuration of this application.</p>
							<h3>Compatibility</h3>
							<p>The application has been tested and proved to work on the Server version: Apache/2.2.16 (Ubuntu)</p>
							<p>The user must also use a compatible browser, with JavaScript and Adobe Flash enabled.</p>
							<p>Compatible browsers with the application are: Chrome v10.648+, Firefox 3.6.16+. The application may work in other browsers, but compatibility cannot be
							guaranteed.</p>
							<h3>Framework</h3>
							<p>The application has been developed in PHP by using the CodeIgniter Framework and it uses a MySQL database.</p>
							<p>More information about the CodeIgniter Framework can be found in the <a href="http://codeigniter.com/user_guide/" target="_blank">framework user manual</a>.
							<h2>Completion Time</h2>
							<p>Completion time is used to measure the time spent by a system to perform a task.</p>
							<p>This application permits you to view the completion time constraint violations of a PHP web application
							developed using the UML2QoS plug-in for Eclipse.</p>
							<p>On the completion time page, the user can see <b>First completion time</b> and <b>Last completion time</b>,
							these values represent the first and the last constraint violations registered in the databse by the instrumentation
							code embedded in the monitored application, by the UML2QoS plugin.</p>
							<h3>Completion time selection form</h3>
							<p>On the completion time page, users can use a form to select specific completion time constraint violations
							that they are interested in.</p>
							<p>The <b>Show</b> input, asks the user to insert the number of requests he wants
							to have displayed in the graph. This value can be anything between 1 and 3000. The number of constraints is
							limited to 3000 because higher values can cause instability in the Flash plug-in and can possibly freesze the 
							user's browser is a slower computer is used.</p>
							<p>The <b>requests for</b> drop down, gives the user to filter the requests by the method in which the constraint
							violations have occured. Different methods can have different constraints.</p>
							<p>The <b>over</b> input asks the user to give the minimum completion time generated by the chosen requests. The value is in
							seconds and can have 8 digits in total.</p>
							<p>The <b>seconds, starting from</b> input field asks the user to provide the start time from when the requests are counted.
							The value can be selected by using the TimePicker plug-in, or can be typed in manually by following this format:
							Day-Month-Year HH:MM.</p>
							<h3>Completion time graph</h3>
							<p>The user must have Adobe Flash installed in order to use the graph.</p>
							<p>The <b>graph</b> allows the users to zoom in on the data, by using the mouse to select an interval. After zooming in
							the users can navigate through the graph by using the grey bar at the top of the graph. To return to the initial state 
							of the graph, the user has to click on the Show All button in the top left of the graph.</p>
							<h2>Arrival Rate</h2>
							<p>Arrival rate is used to measure the total number of requests per time unit.</p>
							<p>The application allows the user to see the arrival rate of all the intrumented methods over the last 24 hours, by default, once
							the page is loaded.</p>
							<p>On the arrival rate page, the user can see <b>First recorded request</b> and the <b>Last recorded request</b>,
							these values represent the first and the last instrumented values stored in the databse by the arrival rate measuring
							code embedded in the monitored application, by the UML2QoS plugin.</p>
							<p>The user can use the arrival rate form to obtain a more specific value, either for only one method or between a specific
							time interval.</p>
							<p>The <b>For</b> drop-down allows the user to choose for which instrumented method the arrival rate is calculated.</p>
							<p>The next two input forms, namely <b>starting from</b> and <b>ending at</b>, are used to specify the time intervals used
							in the calculation of the arrival rate.</p>
							<h2>Accessibility</h2>
							<p>Accessibility is used to measure the percentage of requests which received a response from the system</p>
							<p>The application allows the user to see the accessibility of all the instrumented methods over the last 24 hours, by default, once
							the page is loaded.</p>
							<p>On the accessibility page, the user can see <b>First recorded request</b> and the <b>Last recorded request</b>,
							these values represent the first and the last instrumented values stored in the databse by the arrival rate measuring
							code embedded in the monitored application, by the UML2QoS plugin.</p>
							<p>The user can use the accessibility form to obtain a more specific value of the metric, by choosing only one of the instrumented
							methods and by specifying the time intervals during which the metric should be calculated.</p>
							<p>The <b>For</b> drop-down allows the user to choose for which instrumented method the accessibility is calculated.</p>
							<p>The next two input forms, namely <b>starting from</b> and <b>ending at</b>, are used to specify the time intervals used
							in the calculation of the accessibility metric.</p>
							<h2>Throughput</h2>	
							<p>Throughput represents the number of completed requests handled by a system in a given time interval. This metric
							is very similar to accessibility, the only difference is that it shows the result in requests processed per second.</p>
							<p>On the throughput page, the user can see <b>First recorded request</b> and the <b>Last recorded request</b>,
							these values represent the first and the last instrumented values stored in the databse by the arrival rate measuring
							code embedded in the monitored application, by the UML2QoS plugin.</p>
							<p>The user can use the throughput form to obtain a more specific value of the metric, by choosing only one of the instrumented
							methods and by specifying the time intervals during which the metric should be calculated.</p>
							<p>The <b>For</b> drop-down allows the user to choose for which instrumented method the throughput is calculated.</p>
							<p>The next two input forms, namely <b>starting from</b> and <b>ending at</b>, are used to specify the time intervals used
							in the calculation of the throughout metric.</p>							
						</div>
					</div>
					<div class="clear"></div>
				</div><!-- End container -->